SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 55959: SAS® Deployment Manager tries to perform an upgrade in-place for SAS® Environment Manager Architecture when you upgrade SAS® 9.4 TS1M2

DetailsHotfixAboutRate It

The second maintenance release for SAS 9.4 (TS1M2), Revision 942_14w41 and later includes SAS Environment Manager Service Architecture components, which is also known as SAS Environment Manager Kit Enablement Server. When you perform an upgrade in-place from SAS 9.4 TS1M2, Revision xxx_14w41 or later to SAS 9.4 TS1M3, SAS Deployment Manager attempts to perform an upgrade in-place on the Service Architecture. This attempt happens even if this component is not initialized or enabled. If the component is not initialized, there is no need to perform the upgrade.

When the unnecessary upgrade is attempted, error messages are generated. One such message is shown below:

image label

Although the configuration process will not be interrupted and should complete successfully, the status bubble next to the task is yellow (indicating a warning), and messages indicating that there are problems are included in the upgradeInstructions.html file that is generated.

If the Service Architecture is not initialized, you can safely ignore these messages. There should be no impact (negative or otherwise) on the upgraded deployment.

If you decide to enable the Service Architecture, the first step in the Service Architecture Quickstart guide states that you should run the validation script. (The Quickstart guide is available in SAS-configuration-directory\Lev1\Web\SASEnvironmentManager\emi-framework. The information is also available in the section "SAS Environment Manager Extended Monitoring Steps" in "Chapter 9: Initializing and Enabling the Service Management Architecture" of the SAS Environment Manager 2.4: User's Guide." In this scenario, the validation step fails, and you receive the following message indicating that an upgrade is pending and must be completed before the initialization process can continue.

my-server> bin/validate.sh --level 2
Service Architecture Validation - Fri May 29 13:11:47 EDT 2015 
Starting level 1 validation... 
Level 1 validation completed with 1 error(s)

Starting extended level 2 validation (this could take a while)...
Level 2 validation completed with 0 error(s) in 20.869 sec
Service Architecture validation completed with 1 error(s)
Errors: 
1)	Upgrade-in-place has not completed successfully. Run the ugip_init command.

To avoid this problem, perform the following steps before you validate the script:

  1. Locate the sasev.properties file that resides in the Service Architecture root directory. The default location is SAS-configuration-directory\Lev1\Web\SASEnvironmentManager\emi-framework.
  2. In sasev.properties, search for the property that is named ugipStatus. This proper should have a value of pending. Change that property value to notNeeded and save the modified file.
  3. Move the original deployment’s Service Architecture root directory to another location to free a small amount of disk space and eliminate any potential confusion.
  4. Rerun the validation script. The script should run successfully.
  5. Complete the remaining initialization steps.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Environment Manager Enablement Kit ServerMicrosoft Windows 8 Enterprise 32-bit2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows 8 Enterprise x642.42.59.4 TS1M39.4 TS1M3
Microsoft Windows 8 Pro 32-bit2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows 8 Pro x642.42.59.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Enterprise 32-bit2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Enterprise x642.42.59.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Pro2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Pro 32-bit2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows Server 20082.42.59.4 TS1M39.4 TS1M3
Microsoft Windows Server 2008 R22.42.59.4 TS1M39.4 TS1M3
Microsoft Windows Server 2008 for x642.42.59.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 Datacenter2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 R2 Datacenter2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 R2 Std2.42.59.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 Std2.42.59.4 TS1M39.4 TS1M3
Windows 7 Enterprise 32 bit2.42.59.4 TS1M39.4 TS1M3
Windows 7 Enterprise x642.42.59.4 TS1M39.4 TS1M3
Windows 7 Home Premium 32 bit2.42.59.4 TS1M39.4 TS1M3
Windows 7 Home Premium x642.42.59.4 TS1M39.4 TS1M3
Windows 7 Professional 32 bit2.42.59.4 TS1M39.4 TS1M3
Windows 7 Professional x642.42.59.4 TS1M39.4 TS1M3
Windows 7 Ultimate 32 bit2.42.59.4 TS1M39.4 TS1M3
Windows 7 Ultimate x642.42.59.4 TS1M39.4 TS1M3
64-bit Enabled AIX2.42.59.4 TS1M39.4 TS1M3
64-bit Enabled Solaris2.42.59.4 TS1M39.4 TS1M3
HP-UX IPF2.42.59.4 TS1M39.4 TS1M3
Linux for x642.42.59.4 TS1M39.4 TS1M3
Solaris for x642.42.59.4 TS1M39.4 TS1M3
Microsoft® Windows® for x642.42.59.4 TS1M29.4 TS1M3
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.